From 8841adb37a7536b4b070d90ccaafcf5e1f039225 Mon Sep 17 00:00:00 2001 From: Lute Kamstra Date: Mon, 6 Oct 2003 08:26:26 +0000 Subject: [PATCH] (Coding Conventions): Mention naming conventions for hooks. --- lispref/tips.texi | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/lispref/tips.texi b/lispref/tips.texi index d769fca581d..d07fa1b3712 100644 --- a/lispref/tips.texi +++ b/lispref/tips.texi @@ -125,6 +125,12 @@ add @samp{-p}. Examples are @code{framep} and @code{frame-live-p}. If a user option variable records a true-or-false condition, give it a name that ends in @samp{-flag}. +@item +If the purpose of a variable is to store a single function, give it a +name that ends in @samp{-function}. If the purpose of a variable is +to store a list of functions (i.e., the variable is a hook), please +follow the naming conventions for hooks. @xref{Hooks}. + @item @cindex reserved keys @cindex keys, reserved -- 2.30.2